UCF STIG Viewer Logo
Changes are coming to https://stigviewer.com. Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey

The IDPS must provide audit record generation with a configurable severity and escalation level capability.


Overview

Finding ID Version Rule ID IA Controls Severity
V-55321 SRG-NET-000113-IDPS-00189 SV-69567r2_rule Medium
Description
Without the capability to generate audit records with a severity code it is difficult to track and handle detection events. While auditing and logging are closely related, they are not the same. Logging is recording data about events that take place in a system, while auditing is the use of log records to identify security-relevant information such as system or user accesses. In short, log records are audited to establish an accurate history. Without logging, it would be impossible to establish an audit trail. The IDPS must have the capability to collect and log the severity associated with the policy, rule, or signature. IDPS products often have either pre-configured and/or a configurable method for associating an impact indicator or severity code with signatures and rules, at a minimum.
STIG Date
Intrusion Detection and Prevention Systems (IDPS) Security Requirements Guide 2020-06-12

Details

Check Text ( C-55943r1_chk )
Verify the configuration provides audit record generation with a configurable severity and escalation level capability.

If the IDPS does not provide audit record generation with a configurable severity and escalation level capability, this is a finding.
Fix Text (F-60187r1_fix)
Configure the IDPS to provide audit record generation with a configurable severity and escalation level capability.